SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Software-defined networking</title>

</head>

Software-defined networking

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Not to be confused with <a href="Integrated_Services_Digital_Network" class="mw-redirect" title="Integrated Services Digital Network">ISDN (Integrated Services Digital Network)</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1248332772">

/* start https://en.wikipedia.org/ */

.mw-parser-output .multiple-issues-text{width:95%;margin:0.2em 0}.mw-parser-output .multiple-issues-text>.mw-collapsible-content{margin-top:0.3em}.mw-parser-output .compact-ambox .ambox{border:none;border-collapse:collapse;background-color:transparent;margin:0 0 0 1.6em!important;padding:0!important;width:auto;display:block}body.mediawiki .mw-parser-output .compact-ambox .ambox.mbox-small-left{font-size:100%;width:auto;margin:0}.mw-parser-output .compact-ambox .ambox .mbox-text{padding:0!important;margin:0!important}.mw-parser-output .compact-ambox .ambox .mbox-text-span{display:list-item;line-height:1.5em;list-style-type:disc}body.skin-minerva .mw-parser-output .multiple-issues-text>.mw-collapsible-toggle,.mw-parser-output .compact-ambox .ambox .mbox-image,.mw-parser-output .compact-ambox .ambox .mbox-imageright,.mw-parser-output .compact-ambox .ambox .mbox-empty-cell,.mw-parser-output .compact-ambox .hide-when-compact{display:none}

/* end https://en.wikipedia.org/ */

</style>

Software-defined networking (SDN) is an approach to <a href="Network_management" title="Network management">network management</a> that uses abstraction to enable dynamic and programmatically efficient network configuration to create grouping and segmentation while improving network performance and monitoring in a manner more akin to <a href="Cloud_computing" title="Cloud computing">cloud computing</a> than to traditional network management.<a href="#cite_note-ReferenceA-1">[1]</a> SDN is meant to improve the static architecture of traditional networks and may be employed to centralize network intelligence in one network component by disassociating the forwarding process of <a href="Network_packet" title="Network packet">network packets</a> (<a href="Data_plane" title="Data plane">data plane</a>) from the routing process (<a href="Control_plane" title="Control plane">control plane</a>).<a href="#cite_note-2">[2]</a> The control plane consists of one or more controllers, which are considered the brains of the SDN network, where the whole intelligence is incorporated. However, centralization has certain drawbacks related to security,<a href="#cite_note-ReferenceA-1">[1]</a> scalability and elasticity.<a href="#cite_note-ReferenceA-1">[1]</a><a href="#cite_note-3">[3]</a>

SDN was commonly associated with the <a href="OpenFlow" title="OpenFlow">OpenFlow</a> protocol for remote communication with network plane elements to determine the path of <a href="Network_packet" title="Network packet">network packets</a> across <a href="Network_switch" title="Network switch">network switches</a> since OpenFlow's emergence in 2011. However, since 2012, proprietary systems have also used the term.<a href="#cite_note-TechTarget:_SDN_is_not_OpenFlow-4">[4]</a><a href="#cite_note-TechTarget:_OpenFlow_not_the_only_show_in_town-5">[5]</a> These include <a href="Cisco_Systems" class="mw-redirect" title="Cisco Systems">Cisco Systems</a>' Open Network Environment and <a href="Nicira" title="Nicira">Nicira</a>'s <a href="Network_virtualization_platform" title="Network virtualization platform">network virtualization platform</a>.

<a href="SD-WAN" title="SD-WAN">SD-WAN</a> applies similar technology to a <a href="Wide_area_network" title="Wide area network">wide area network</a> (WAN).<a href="#cite_note-6">[6]</a>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

The history of SDN principles can be traced back to the separation of the control and data planes first used in public switched telephone networks. This provided a manner of simplifying provisioning and management years before the architecture was used in data networks.

The <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF) began considering various ways to decouple the control and data forwarding functions in a proposed interface standard published in 2004 named Forwarding and Control Element Separation (ForCES).<a href="#cite_note-7">[7]</a> The ForCES Working Group also proposed a companion SoftRouter architecture.<a href="#cite_note-8">[8]</a> Additional early standards from the IETF that pursued separating control from data planes include the Linux Netlink as an IP services protocol,<a href="#cite_note-9">[9]</a> and a path computation element (PCE)-based architecture.<a href="#cite_note-10">[10]</a>

These early attempts failed to gain traction. One reason is that many in the Internet community viewed separating control from data to be risky, especially given the potential for failure in the control plane. Another reason is that vendors were concerned that creating standard application programming interfaces (APIs) between the control and data planes would result in increased competition.

The use of open-source software in these separated architectures traces its roots to the Ethane project at <a href="Stanford" class="mw-redirect" title="Stanford">Stanford</a>'s computer science department. Ethane's simple switch design led to the creation of OpenFlow,<a href="#cite_note-11">[11]</a> and an API for OpenFlow was first created in 2008.<a href="#cite_note-12">[12]</a> In that same year, NOX, an operating system for networks, was created.<a href="#cite_note-13">[13]</a>

SDN research included <a href="Emulator" title="Emulator">emulators</a> such as vSDNEmul,<a href="#cite_note-14">[14]</a> EstiNet,<a href="#cite_note-15">[15]</a> and Mininet.<a href="#cite_note-16">[16]</a>

Work on OpenFlow continued at Stanford, including with the creation of testbeds to evaluate the use of the protocol in a single campus network, as well as across the WAN as a backbone for connecting multiple campuses.<a href="#cite_note-17">[17]</a> In academic settings, there were several research and production networks based on OpenFlow switches from <a href="NEC" title="NEC">NEC</a> and <a href="Hewlett-Packard" title="Hewlett-Packard">Hewlett-Packard</a>, as well as those based on <a href="Quanta_Computer" title="Quanta Computer">Quanta Computer</a> white-boxes starting in about 2009.<a href="#cite_note-18">[18]</a>

Beyond academia, the first deployments were by <a href="Nicira" title="Nicira">Nicira</a> in 2010 to control OVS from Onix, codeveloped with NTT and Google. A notable deployment was <a href="Google" title="Google">Google</a>'s B4 in 2012.<a href="#cite_note-19">[19]</a><a href="#cite_note-20">[20]</a> Later, Google announced the first OpenFlow/Onix deployments in is datacenters.<a href="#cite_note-21">[21]</a> Another large deployment exists at <a href="China_Mobile" title="China Mobile">China Mobile</a>.<a href="#cite_note-22">[22]</a>

The <a href="Open_Networking_Foundation" title="Open Networking Foundation">Open Networking Foundation</a> was founded in 2011 to promote SDN and OpenFlow.

At the 2014 Interop and Tech Field Day, software-defined networking was demonstrated by <a href="Avaya" title="Avaya">Avaya</a> using shortest-path bridging (<a href="IEEE_802.1aq" title="IEEE 802.1aq">IEEE 802.1aq</a>) and <a href="OpenStack" title="OpenStack">OpenStack</a> as an automated campus, extending automation from the data center to the end device and removing manual provisioning from service delivery.<a href="#cite_note-23">[23]</a><a href="#cite_note-24">[24]</a>

<div class="mw-heading mw-heading2"><h2 id="Concept">Concept</h2></div>

SDN architectures decouple network control (<a href="Control_plane" title="Control plane">control plane</a>) and forwarding (<a href="Data_plane" title="Data plane">data plane</a>) functions, enabling the network control to become directly programmable and the underlying infrastructure to be abstracted from applications and network services.<a href="#cite_note-25">[25]</a> The OpenFlow protocol is one of the protocols used in SDN technologies.

The SDN architecture is:

<ul><li>Directly programmable: Network control is directly programmable because it is decoupled from forwarding functions.</li>

<li>Agile: Abstracting control from forwarding lets administrators dynamically adjust network-wide <a href="Traffic_flow_(computer_networking)" title="Traffic flow (computer networking)">traffic flow</a> to meet changing needs.</li>

<li>Centrally managed: Network intelligence is (logically) centralized in software-based SDN controllers that maintain a global view of the network, which appears to applications and policy engines as a single, logical switch.</li>

<li>Programmatically configured: SDN lets network managers configure, manage, secure, and optimize network resources very quickly via dynamic, automated SDN programs, which they can write themselves because the programs do not depend on proprietary software.<a href="#cite_note-26">[26]</a></li>

<li>Open standards-based and vendor-neutral: When implemented through open standards, SDN simplifies network design and operation because instructions are provided by SDN controllers instead of multiple, vendor-specific devices and protocols.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="New_network_architecture">New network architecture</h2></div>

The explosion of mobile devices and content, server virtualization, and the advent of cloud services are among the trends driving the networking industry to re-examine traditional network architectures.<a href="#cite_note-27">[27]</a> Many conventional networks are hierarchical, built with tiers of Ethernet switches arranged in a tree structure. This design made sense when client-server computing was dominant, but such a static architecture may be ill-suited to the dynamic computing and storage needs of today's enterprise data centers, campuses, and carrier environments.<a href="#cite_note-28">[28]</a> Some of the key computing trends driving the need for a new network paradigm include:

<dl><dt>Changing traffic patterns</dt>

<dd>Within the enterprise data center, traffic patterns have changed significantly. In contrast to client-server applications where the bulk of the communication occurs between one client and one server, today's applications access different databases and servers, creating a flurry of <a href="East-west_traffic" title="East-west traffic">east-west machine-to-machine traffic</a> before returning data to the end user device in the classic <a href="North-south_traffic" title="North-south traffic">north-south traffic</a> pattern. At the same time, users are changing network traffic patterns as they push for access to corporate content and applications from any type of device, connecting from anywhere, at any time. Finally, many enterprise data center managers are deploying a utility computing model, which may include a private cloud, public cloud, or some mix of both, resulting in additional traffic across the wide-area network.</dd></dl>

<dl><dt>The consumerization of IT</dt>

<dd>Users are increasingly employing mobile personal devices such as smartphones, tablets, and notebooks to access the corporate network. IT is under pressure to accommodate these personal devices in a fine-grained manner while protecting corporate data and intellectual property and meeting compliance mandates.</dd></dl>

<dl><dt>The rise of cloud services</dt>

<dd>Enterprises have enthusiastically embraced both public and private cloud services, resulting in unprecedented growth of these services. Many enterprise businesses want the agility to access applications, infrastructure and other IT resources on demand and discretely. IT planning for cloud services must be performed in an environment of increased security, compliance and auditing requirements, along with business reorganizations, consolidations and mergers that can rapidly change assumptions. Providing self-service provisioning, whether in a private or public cloud, requires elastic scaling of computing, storage and network resources, ideally from a common viewpoint and with a common suite of tools.</dd></dl>

<dl><dt>Big data means more bandwidth</dt>

<dd>Handling today's <a href="Big_data" title="Big data">big data</a> requires massive parallel processing on thousands of servers, all of which need direct connections to each other. The rise of these large <a href="Data_set" title="Data set">data sets</a> is fueling a constant demand for additional network capacity in the data center. Operators of hyperscale data center networks face the daunting task of scaling the network to previously unimaginable size, maintaining any-to-any connectivity within a limited budget.<a href="#cite_note-29">[29]</a></dd></dl>

<dl><dt>Energy use in large data centers</dt>

<dd>As <a href="Internet_of_things" title="Internet of things">Internet of things</a>, <a href="Cloud_computing" title="Cloud computing">cloud computing</a> and <a href="SaaS" class="mw-redirect" title="SaaS">SaaS</a> emerged, the need for larger data centers has increased the energy consumption of those facilities. Many researchers have improved SDN's <a href="Efficient_energy_use" title="Efficient energy use">energy efficiency</a> applying existing routing techniques to dynamically adjust the network data plane to save energy.<a href="#cite_note-30">[30]</a> Also techniques to improve control plane energy efficiency are being researched.<a href="#cite_note-31">[31]</a></dd></dl>

<div class="mw-heading mw-heading2"><h2 id="Architectural_components">Architectural components</h2></div>

The following list defines and explains the SDN architectural components:<a href="#cite_note-32">[32]</a>

<dl><dt>SDN application</dt>

<dd>SDN applications are programs that communicate their network requirements and desired network behavior to the SDN controller via a <a href="Northbound_interface" title="Northbound interface">northbound interface</a> (NBI). In addition, they may consume an abstracted view of the network for their internal decision-making purposes. An SDN Application consists of SDN application logic and one or more NBI drivers. SDN applications may themselves expose another layer of abstracted network control, thus offering one or more higher-level NBIs through respective NBI agents.</dd></dl>

<dl><dt>SDN controller</dt>

<dd>The SDN controller is a logically centralized entity in charge of (i) translating the requirements from the SDN application layer down to the SDN datapaths and (ii) providing the SDN applications with an abstract view of the network (which may include statistics and events). An SDN controller consists of one or more NBI agents, the SDN control logic, and the control to data-plane interface (CDPI) driver. The controller's definition as a logically centralized entity neither prescribes nor precludes implementation architectures such as the federation of multiple controllers, the hierarchical connection of controllers, communication interfaces between controllers, nor virtualization or slicing of network resources.</dd></dl>

<dl><dt>SDN datapath</dt>

<dd>The SDN datapath is a logical network device that exposes visibility and uncontested control over its advertised forwarding and data processing capabilities. The logical representation may encompass all or a subset of the capabilities. An SDN datapath consists of a CDPI agent and a set of one or more traffic forwarding engines and zero or more traffic processing functions. These engines and functions may include simple forwarding between the datapath's external interfaces or internal traffic processing or termination functions. One or more SDN datapaths may be contained in a single (physical) network element—an integrated physical combination of communications resources, managed as a unit. An SDN datapath may also be defined across multiple physical network elements. This logical definition neither prescribes nor precludes implementation details such as the logical to physical mapping, management of shared physical resources, virtualization or slicing of the SDN datapath, interoperability with non-SDN networking, nor the data processing functionality, which can include <a href="OSI_model" title="OSI model">OSI layer 4-7</a> functions.</dd></dl>

<dl><dt>SDN Control to Data-Plane Interface (CDPI)</dt>

<dd>The SDN CDPI is the interface defined between an SDN controller and an SDN datapath, which provides at least programmatic control of all forwarding operations, capabilities advertisement, statistics reporting, and event notification. One value of SDN lies in the expectation that the CDPI is implemented in an open, vendor-neutral and interoperable way.</dd></dl>

<dl><dt>SDN Northbound Interfaces (NBI)</dt>

<dd>SDN NBIs are interfaces between SDN applications and SDN controllers and typically provide abstract network views and enable direct expression of network behavior and requirements. This may occur at any level of abstraction and across different sets of functionality.</dd></dl>

<div class="mw-heading mw-heading2"><h2 id="SDN_control_plane">SDN control plane</h2></div>

The implementation of the SDN control plane can follow a centralized, hierarchical, or decentralized design. Initial SDN control plane proposals focused on a centralized solution, where a single control entity had a global view of the network. While this simplifies the implementation of the control logic, it has scalability limitations as the size and dynamics of the network increase. To overcome these limitations, hierarchical and distributed approaches have been proposed. In hierarchical solutions,<a href="#cite_note-Yeganeh-33">[33]</a><a href="#cite_note-Ahmed-34">[34]</a> controllers operate on a partitioned network view, while decisions that require network-wide knowledge are taken by a logically centralized root controller. In distributed approaches,<a href="#cite_note-Koponen-35">[35]</a><a href="#cite_note-Tuncer1-36">[36]</a> controllers operate on their local view or they may exchange synchronization messages to enhance their knowledge. Distributed solutions are more suitable for supporting adaptive SDN applications.

A key issue when designing a distributed SDN control plane is to decide on the number and placement of control entities. An important parameter to consider while doing so is the <a href="Network_delay" title="Network delay">propagation delay</a> between the controllers and the network devices,<a href="#cite_note-Heller-37">[37]</a> especially in the context of large networks. Other objectives that have been considered involve control path <a href="Reliability_(computer_networking)" title="Reliability (computer networking)">reliability</a>,<a href="#cite_note-Hu-38">[38]</a> <a href="Fault_tolerance" title="Fault tolerance">fault tolerance</a>,<a href="#cite_note-Ros-39">[39]</a> and application requirements.<a href="#cite_note-Tuncer2-40">[40]</a>

<div class="mw-heading mw-heading2"><h2 id="SDN_Data_Plane">SDN Data Plane</h2></div>

In SDN, the data plane is responsible for processing data-carrying packets using a set of rules specified by the control plane. The data plane may be implemented in physical hardware switches or in software implementations, such as <a href="Open_vSwitch" title="Open vSwitch">Open vSwitch</a>. The memory capacity of hardware switches may limit the number of rules that can be stored where as software implementations may have higher capacity.<a href="#cite_note-wang.2014.scotch-41">[41]</a>

The location of the SDN data plane and agent can be used to classify SDN implementations:

<ul><li>Hardware Switch-based SDNs: This approach implements the data plane processing inside a physical device. OpenFlow switches may use <a href="Content-addressable_memory#Ternary_CAMs" title="Content-addressable memory">TCAM</a> tables to route packet sequences <a href="Traffic_flow_(computer_networking)" title="Traffic flow (computer networking)">(flows)</a>. These switches may use an <a href="ASIC" class="mw-redirect" title="ASIC">ASIC</a> for its implementation.</li></ul>

<ul><li>Software Switch-Based SDNs: Some physical switches may implement SDN support using software on the device, such as <a href="Open_vSwitch" title="Open vSwitch">Open vSwitch</a>, to populate flow tables and to act as the SDN agent when communicating with the controller. <a href="Hypervisor" title="Hypervisor">Hypervisors</a> may likewise use software implementations to support SDN protocols in the virtual switches used to support their <a href="Virtual_machine" title="Virtual machine">virtual machines</a>.</li></ul>

<ul><li>Host-Based SDNs: Rather than deploying the data plane and SDN agent in network infrastructure, host-based SDNs deploy the SDN agent inside the operating system of the communicating endpoints.<a href="#cite_note-42">[42]</a> Such implementations can provide additional context about the application, user, and activity associated with network flows.<a href="#cite_note-43">[43]</a> To achieve the same traffic engineering capabilities of switch-based SDNs, host-based SDNs may require the use of carefully designed <a href="VLAN" title="VLAN">VLAN</a> and <a href="Spanning_Tree_Protocol" title="Spanning Tree Protocol">spanning tree</a> assignments.<a href="#cite_note-44">[44]</a></li></ul>

Flow table entries may be populated in a proactive, reactive, or hybrid fashion.<a href="#cite_note-45">[45]</a><a href="#cite_note-46">[46]</a> In the proactive mode, the controller populates flow table entries for all possible traffic matches possible for this switch in advance. This mode can be compared with typical routing table entries today, where all static entries are installed ahead of time. Following this, no request is sent to the controller since all incoming flows will find a matching entry. A major advantage in proactive mode is that all packets are forwarded in line rate (considering all flow table entries in TCAM) and no delay is added. In the reactive mode, entries are populated on demand. If a packet arrives without a corresponding match rule in the flow table, the SDN agent sends a request to the controller for further instruction it the reactive mode. The controller examines the SDN agent requests and provides instructions, installing a rule in the flow table for the corresponding packet if necessary. The hybrid mode uses the low-latency proactive forwarding mode for a portion of traffic while relying on the flexibility of reactive mode processing for the remaining traffic.

<div class="mw-heading mw-heading2"><h2 id="Applications">Applications</h2></div>

<a href="Software-defined_mobile_network" title="Software-defined mobile network">Software-defined mobile networking</a> (SDMN)<a href="#cite_note-MobileFlow-47">[47]</a><a href="#cite_note-48">[48]</a> is an approach to the design of mobile networks where all protocol-specific features are implemented in software, maximizing the use of generic and commodity hardware and software in both the <a href="Core_network" class="mw-redirect" title="Core network">core network</a> and <a href="Radio_access_network" title="Radio access network">radio access network</a>.<a href="#cite_note-49">[49]</a> It is proposed as an extension of SDN paradigm to incorporate <a href="Mobile_network" class="mw-redirect" title="Mobile network">mobile network</a> specific functionalities.<a href="#cite_note-50">[50]</a> Since 3GPP Rel.14, a Control User Plane Separation was introduced in the Mobile Core Network architectures with the <a href="PFCP" title="PFCP">PFCP</a> protocol.

An <a href="SD-WAN" title="SD-WAN">SD-WAN</a> is a WAN managed using the principles of software-defined networking.<a href="#cite_note-51">[51]</a> The main driver of SD-WAN is to lower WAN costs using more affordable and commercially available leased lines, as an alternative or partial replacement of more expensive <a href="MPLS" class="mw-redirect" title="MPLS">MPLS</a> lines. Control and management is administered separately from the hardware with central controllers allowing for easier configuration and administration.<a href="#cite_note-networkworld1-52">[52]</a>

An SD-LAN is a <a href="Local_area_network" title="Local area network">Local area network</a> (LAN) built around the principles of software-defined networking, though there are key differences in topology, network security, application visibility and control, management and quality of service.<a href="#cite_note-53">[53]</a> SD-LAN decouples control management, and data planes to enable a policy driven architecture for wired and wireless LANs. SD-LANs are characterized by their use of a cloud management system and wireless connectivity without the presence of a physical controller.<a href="#cite_note-54">[54]</a>

<div class="mw-heading mw-heading3"><h3 id="Security_using_the_SDN_paradigm">Security using the SDN paradigm</h3></div>

SDN architecture may enable, facilitate or enhance network-related security applications due to the controller's central view of the network, and its capacity to reprogram the data plane at any time. While the security of SDN architecture itself remains an open question that has already been studied a couple of times in the research community,<a href="#cite_note-kreutz2013towards-55">[55]</a><a href="#cite_note-scott2013sdn-56">[56]</a><a href="#cite_note-benton2013openflow-57">[57]</a><a href="#cite_note-58">[58]</a> the following paragraphs only focus on the security applications made possible or revisited using SDN.

Several research works on SDN have already investigated security applications built upon the SDN controller, with different aims in mind. Distributed Denial of Service (DDoS) detection and mitigation,<a href="#cite_note-giotis2014combining-59">[59]</a><a href="#cite_note-braga2010lightweight-60">[60]</a> as well as botnet<a href="#cite_note-feamster2010outsourcing-61">[61]</a> and worm propagation,<a href="#cite_note-jin2013malware-62">[62]</a> are some concrete use-cases of such applications: basically, the idea consists in periodically collecting network statistics from the forwarding plane of the network in a standardized manner (e.g. using Openflow), and then apply classification algorithms on those statistics in order to detect any network anomalies. If an anomaly is detected, the application instructs the controller how to reprogram the data plane in order to mitigate it.

Another kind of security application leverages the SDN controller by implementing some moving target defense (MTD) algorithms. MTD algorithms are typically used to make any attack on a given system or network more difficult than usual by periodically hiding or changing key properties of that system or network. In traditional networks, implementing MTD algorithms is not a trivial task since it is difficult to build a central authority able of determining - for each part of the system to be protected - which key properties are hidden or changed. In an SDN network, such tasks become more straightforward thanks to the centrality of the controller. One application can for example periodically assign virtual IPs to hosts within the network, and the mapping virtual IP/real IP is then performed by the controller.<a href="#cite_note-jafarian2012openflow-63">[63]</a> Another application can simulate some fake opened/closed/filtered ports on random hosts in the network in order to add significant noise during reconnaissance phase (e.g. scanning) performed by an attacker.<a href="#cite_note-kampanakissdn-64">[64]</a>

Additional value regarding security in SDN enabled networks can also be gained using FlowVisor<a href="#cite_note-sherwood2009flowvisor-65">[65]</a> and FlowChecker<a href="#cite_note-al2010flowchecker-66">[66]</a> respectively. The former tries to use a single hardware forwarding plane sharing multiple separated logical networks. Following this approach the same hardware resources can be used for production and development purposes as well as separating monitoring, configuration and internet traffic, where each scenario can have its own logical topology which is called slice. In conjunction with this approach FlowChecker<a href="#cite_note-sherwood2009flowvisor-65">[65]</a> realizes the validation of new OpenFlow rules that are deployed by users using their own slice.

SDN controller applications are mostly deployed in large-scale scenarios, which requires comprehensive checks of possible programming errors. A system to do this called NICE was described in 2012.<a href="#cite_note-canini2012nice-67">[67]</a> Introducing an overarching security architecture requires a comprehensive and protracted approach to SDN. Since it was introduced, designers are looking at possible ways to secure SDN that do not compromise scalability. One architecture called SN-SECA (SDN+NFV) Security Architecture.<a href="#cite_note-bernardo2015sn-seca-68">[68]</a>

<div class="mw-heading mw-heading3"><h3 id="Group_Data_Delivery_Using_SDN">Group Data Delivery Using SDN</h3></div>

Distributed applications that run across datacenters usually replicate data for the purpose of synchronization, fault resiliency, load balancing and getting data closer to users (which reduces latency to users and increases their perceived throughput). Also, many applications, such as Hadoop, replicate data within a datacenter across multiple racks to increase fault tolerance and make data recovery easier. All of these operations require data delivery from one machine or datacenter to multiple machines or datacenters. The process of reliably delivering data from one machine to multiple machines is referred to as Reliable Group Data Delivery (RGDD).

SDN switches can be used for RGDD via installation of rules that allow forwarding to multiple outgoing ports. For example, OpenFlow provides support for Group Tables since version 1.1<a href="#cite_note-69">[69]</a> which makes this possible. Using SDN, a central controller can carefully and intelligently setup forwarding trees for RGDD. Such trees can be built while paying attention to network congestion/load status to improve performance. For example, MCTCP<a href="#cite_note-70">[70]</a> is a scheme for delivery to many nodes inside datacenters that relies on regular and structured topologies of datacenter networks while DCCast<a href="#cite_note-71">[71]</a> and QuickCast<a href="#cite_note-72">[72]</a> are approaches for fast and efficient data and content replication across datacenters over private WANs.

<div class="mw-heading mw-heading2"><h2 id="Relationship_to_NFV">Relationship to NFV</h2></div>

<a href="Network_Function_Virtualization" class="mw-redirect" title="Network Function Virtualization">Network Function Virtualization</a>, or NFV for short, is a concept that complements SDN. Thus, NFV is not dependent on SDN or SDN concepts. NFV separates software from hardware to enable flexible network deployment and dynamic operation. NFV deployments typically use commodity servers to run network services software versions that previously were hardware-based. These software-based services that run in an NFV environment are called Virtual Network Functions (VNF).<a href="#cite_note-Stalling2016-73">[73]</a> SDN-NFV hybrid program was provided for high efficiency, elastic and scalable capabilities NFV aimed at accelerating service innovation and provisioning using standard IT virtualization technologies.<a href="#cite_note-Stalling2016-73">[73]</a><a href="#cite_note-Rowayda2018-74">[74]</a> SDN provides the agility of controlling the generic forwarding devices such as the routers and switches by using SDN controllers. On the other hand, NFV agility is provided for the network applications by using virtualized servers. It is entirely possible to implement a virtualized network function (VNF) as a standalone entity using existing networking and orchestration paradigms. However, there are inherent benefits in leveraging SDN concepts to implement and manage an NFV infrastructure, particularly when looking at the management and orchestration of VNFs, and that's why multivendor platforms are being defined that incorporate SDN and NFV in concerted ecosystems.<a href="#cite_note-75">[75]</a>

<div class="mw-heading mw-heading2"><h2 id="Relationship_to_DPI">Relationship to DPI</h2></div>

<a href="Deep_packet_inspection" title="Deep packet inspection">Deep packet inspection</a> (DPI) provides network with application-awareness, while SDN provides applications with network-awareness.<a href="#cite_note-76">[76]</a> Although SDN will radically change the generic network architectures, it should cope with working with traditional network architectures to offer high interoperability. The new SDN based network architecture should consider all the capabilities that are currently provided in separate devices or software other than the main forwarding devices (routers and switches) such as the DPI, security appliances <a href="#cite_note-ITUDPI-77">[77]</a>

<div class="mw-heading mw-heading2"><h2 id="Quality_of_Experience_(QoE)_estimation_using_SDN">Quality of Experience (QoE) estimation using SDN</h2></div>

When using an SDN based model for transmitting multimedia traffic, an important aspect to take account is the QoE estimation. To estimate the QoE, first we have to be able to classify the traffic and then, it's recommended that the system can solve critical problems on its own by analyzing the traffic.<a href="#cite_note-78">[78]</a><a href="#cite_note-79">[79]</a>

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col" style="column-width: 22em;">

<ul><li><a href="Active_networking" title="Active networking">Active networking</a></li>

<li><a href="Frenetic_(programming_language)" title="Frenetic (programming language)">Frenetic (programming language)</a></li>

<li><a href="Intel_Data_Plane_Development_Kit" class="mw-redirect" title="Intel Data Plane Development Kit">Intel Data Plane Development Kit</a> (DPDK)</li>

<li><a href="List_of_SDN_controller_software" title="List of SDN controller software">List of SDN controller software</a></li>

<li><a href="Network_functions_virtualization" class="mw-redirect" title="Network functions virtualization">Network functions virtualization</a></li>

<li><a href="Network_virtualization" title="Network virtualization">Network virtualization</a></li>

<li><a href="OpenDaylight_Project" title="OpenDaylight Project">OpenDaylight Project</a></li>

<li><a href="Software-defined_data_center" title="Software-defined data center">Software-defined data center</a></li>

<li><a href="Software-defined_mobile_network" title="Software-defined mobile network">Software-defined mobile network</a></li>

<li><a href="Software-defined_protection" title="Software-defined protection">Software-defined protection</a></li>

<li><a href="Virtual_Distributed_Ethernet" title="Virtual Distributed Ethernet">Virtual Distributed Ethernet</a></li></ul>

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFBenzekkiEl_FergouguiElbelrhiti_Elalaoui2016" class="citation journal cs1">Benzekki, Kamal; El Fergougui, Abdeslam; Elbelrhiti Elalaoui, Abdelbaki (2016). "Software-defined networking (SDN): A survey". Security and Communication Networks. 9 (18): 5803–5833. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1002%2Fsec.1737">10.1002/sec.1737</a>.</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite id="CITEREFMontazerolghaem2020" class="citation journal cs1">Montazerolghaem, Ahmadreza (2020-07-13). <a rel="nofollow" class="external text" href="http://link.springer.com/10.1007/s10586-020-03134-x">"Software-defined load-balanced data center: design, implementation and performance analysis"</a>. Cluster Computing. 24 (2): 591–610. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs10586-020-03134-x">10.1007/s10586-020-03134-x</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1386-7857">1386-7857</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:220490312">220490312</a>.</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite id="CITEREFMontazerolghaem2021" class="citation journal cs1">Montazerolghaem, Ahmadreza (2021). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/9475487">"Software-defined Internet of Multimedia Things: Energy-efficient and Load-balanced Resource Management"</a>. IEEE Internet of Things Journal. 9 (3): 2432–2442. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FJIOT.2021.3095237">10.1109/JIOT.2021.3095237</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2327-4662">2327-4662</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:237801052">237801052</a>.</cite>

</li>

<li id="cite_note-TechTarget:_SDN_is_not_OpenFlow-4"><a href="#cite_ref-TechTarget:_SDN_is_not_OpenFlow_4-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://searchsdn.techtarget.com/news/2240158633/Software-defined-networking-is-not-OpenFlow-companies-proclaim">"Software-defined networking is not OpenFlow, companies proclaim"</a>. searchsdn.techtarget.com.</cite>

</li>

<li id="cite_note-TechTarget:_OpenFlow_not_the_only_show_in_town-5"><a href="#cite_ref-TechTarget:_OpenFlow_not_the_only_show_in_town_5-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://searchsdn.techtarget.com/guides/Guide-OpenFlow-SDN-not-the-only-show-in-town-for-vendors">"InCNTRE's OpenFlow SDN testing lab works toward certified SDN product"</a>. 10 February 2016.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://blogs.gartner.com/andrew-lerner/2015/12/15/predicting-sd-wan-adoption/">"Predicting SD-WAN Adoption"</a>. gartner.com. 2015-12-15. Retrieved 2016-06-27.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFL._Yang_(Intel_Corp.),_R._Dantu_(Univ._of_North_Texas),_T._Anderson_(Intel_Corp.)_&_R._Gopal_(Nokia.)2004" class="citation cs1">L. Yang (Intel Corp.), R. Dantu (Univ. of North Texas), T. Anderson (Intel Corp.) & R. Gopal (Nokia.) (April 2004). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3746">Forwarding and Control Element Separation (ForCES) Framework</a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3746">10.17487/RFC3746</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3746">3746</a>.</cite><code class="cs1-code">{{citation}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite id="CITEREFT._V._Lakshman,_T._Nandagopal,_R._Ramjee,_K._Sabnani,_and_T._Woo2004" class="citation web cs1">T. V. Lakshman, T. Nandagopal, R. Ramjee, K. Sabnani, and T. Woo (Nov 2004). <a rel="nofollow" class="external text" href="http://conferences.sigcomm.org/hotnets/2004/HotNets-III%20Proceedings/lakshman.pdf">"The SoftRouter Architecture"</a> (PDF).</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite id="CITEREFJ._Salim_(Znyx_Networks),_H._Khosravi_(Intel),_A._Kleen_(Suse),_and_A._Kuznetsov_(INR/Swsoft)2003" class="citation journal cs1">J. Salim (Znyx Networks), H. Khosravi (Intel), A. Kleen (Suse), and A. Kuznetsov (INR/Swsoft) (July 2003). <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc3549">"Linux Netlink as an IP Services Protocol"</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3549">10.17487/RFC3549</a>.</cite> <code class="cs1-code">{{cite journal}}</code>: Cite journal requires <code class="cs1-code">|journal=</code> (help)CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite id="CITEREFA._Farrel_(Old_Dog_Consulting),_J._Vasseur_(Cisco_Systems,_Inc.),_and_J._Ash_(AT&T)2006" class="citation journal cs1">A. Farrel (Old Dog Consulting), J. Vasseur (Cisco Systems, Inc.), and J. Ash (AT&T) (August 2006). <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc4655">"A Path Computation Element (PCE)-Based Architecture"</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4655">10.17487/RFC4655</a>.</cite> <code class="cs1-code">{{cite journal}}</code>: Cite journal requires <code class="cs1-code">|journal=</code> (help)CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <cite id="CITEREFMartìn_Casado,_Michael_J._Freedman,_Justin_Pettit,_Jianying_Luo,_and_Nick_McKeown_(Stanford_University)2007" class="citation web cs1">Martìn Casado, Michael J. Freedman, Justin Pettit, Jianying Luo, and Nick McKeown (Stanford University) (August 2007). <a rel="nofollow" class="external text" href="http://cs.brown.edu/courses/csci2950-u/s14/papers/Casado07Ethane.pdf">"Ethane: Taking Control of the Enterprise"</a> (PDF).</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <cite id="CITEREFN._McKeown,_T._Anderson,_H._Balakrishnan,_G._Parulkar,_L._Peterson,_J._Rexford,_S._Shenker,_and_J._Turner.2008" class="citation web cs1">N. McKeown, T. Anderson, H. Balakrishnan, G. Parulkar, L. Peterson, J. Rexford, S. Shenker, and J. Turner. (April 2008). <a rel="nofollow" class="external text" href="http://ccr.sigcomm.org/online/files/p69-v38n2n-mckeown.pdf">"OpenFlow: Enabling Innovation in Campus Networks"</a> (PDF).</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite id="CITEREFN._Gude,_T._Koponen,_J._Pettit,_B._Pfaff,_M._Casado,_N._McKeown,_and_S._Shenker.2008" class="citation web cs1">N. Gude, T. Koponen, J. Pettit, B. Pfaff, M. Casado, N. McKeown, and S. Shenker. (July 2008). <a rel="nofollow" class="external text" href="https://benpfaff.org/papers/nox.pdf">"NOX: Towards an Operating System for Networks"</a> (PDF).</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <cite id="CITEREFFariasJuniorda_CostaPinheiro2019" class="citation arxiv cs1">Farias, Fernando N. N.; Junior, Antônio de O.; da Costa, Leonardo B.; Pinheiro, Billy A.; Abelém, Antônio J. G. (2019-08-28). "vSDNEmul: A Software-Defined Network Emulator Based on Container Virtualization". <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<a rel="nofollow" class="external text" href="https://arxiv.org/abs/1908.10980">1908.10980</a> [<a rel="nofollow" class="external text" href="https://arxiv.org/archive/cs.NI">cs.NI</a>].</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite id="CITEREFWangChouYang2013" class="citation journal cs1">Wang, S.; Chou, C.; Yang, C. (September 2013). "EstiNet openflow network simulator and emulator". IEEE Communications Magazine. 51 (9): 110–117. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMCOM.2013.6588659">10.1109/MCOM.2013.6588659</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1558-1896">1558-1896</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:14375937">14375937</a>.</cite>

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <cite id="CITEREFOliveiraSchweitzerShinodaLigia_Rodrigues_Prete2014" class="citation book cs1">Oliveira, R. L. S. de; Schweitzer, C. M.; Shinoda, A. A.; Ligia Rodrigues Prete (June 2014). "Using Mininet for emulation and prototyping Software-Defined Networks". 2014 IEEE Colombian Conference on Communications and Computing (COLCOM). pp. 1–6. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FColComCon.2014.6860404">10.1109/ColComCon.2014.6860404</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4799-4340-1</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17915639">17915639</a>.</cite>

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://groups.geni.net/geni/wiki/OpenFlow/CampusTopology">"GENI. Campus OpenFlow topology"</a>. 2011.</cite>

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> <cite id="CITEREFKuang-Ching_"KC"_Wang2011" class="citation web cs1">Kuang-Ching "KC" Wang (Oct 3, 2011). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103133512/https://www.internet2.edu/presentations/fall11/20111003-wang-openflow.pdf">"Software Defined Networking and OpenFlow for Universities: Motivation, Strategy, and Uses"</a> (PDF). Archived from <a rel="nofollow" class="external text" href="https://www.internet2.edu/presentations/fall11/20111003-wang-openflow.pdf">the original</a> (PDF) on 2018-01-03.</cite>

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> <cite id="CITEREFSushant_Jain,_Alok_Kumar,_Subhasree_Mandal,_Joon_Ong,_Leon_Poutievski,_Arjun_Singh,_Subbaiah_Venkata,_Jim_Wanderer,_Junlan_Zhou,_Min_Zhu,_Jonathan_Zolla,_Urs_Hölzle,_Stephen_Stuart_and_Amin_Vahdat_(Google)2013" class="citation web cs1">Sushant Jain, Alok Kumar, Subhasree Mandal, Joon Ong, Leon Poutievski, Arjun Singh, Subbaiah Venkata, Jim Wanderer, Junlan Zhou, Min Zhu, Jonathan Zolla, Urs Hölzle, Stephen Stuart and Amin Vahdat (Google) (August 12–16, 2013). <a rel="nofollow" class="external text" href="http://cseweb.ucsd.edu/~vahdat/papers/b4-sigcomm13.pdf">"B4: Experience with a Globally-Deployed Software Defined WAN"</a> (PDF).</cite> <code class="cs1-code">{{cite web}}</code>: <code class="cs1-code">|author=</code> has generic name (help)CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> <cite id="CITEREFbrent_salisbury2013" class="citation web cs1">brent salisbury (May 14, 2013). <a rel="nofollow" class="external text" href="https://www.networkcomputing.com/networking/inside-googles-software-defined-network/512240144">"Inside Google's Software-Defined Network"</a>. Network Computing.</cite>

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <cite id="CITEREFArjun_Singh,_Joon_Ong,_Amit_Agarwal,_Glen_Anderson,_Ashby_Armistead,_Roy_Bannon,_Seb_Boving,_Gaurav_Desai,_Bob_Felderman,_Paulie_Germano,_Anand_Kanagala,_Jeff_Provost,_Jason_Simmons,_Eiichi_Tanda,_Jim_Wanderer,_Urs_Hölzle,_Stephen_Stuart,_Amin_Vahdat2015" class="citation web cs1">Arjun Singh, Joon Ong, Amit Agarwal, Glen Anderson, Ashby Armistead, Roy Bannon, Seb Boving, Gaurav Desai, Bob Felderman, Paulie Germano, Anand Kanagala, Jeff Provost, Jason Simmons, Eiichi Tanda, Jim Wanderer, Urs Hölzle, Stephen Stuart, Amin Vahdat (2015). <a rel="nofollow" class="external text" href="https://research.google.com/pubs/pub43837.html">"Jupiter Rising: A Decade of Clos Topologies and Centralized Control in Google's Datacenter Network"</a>.</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.telecomtv.com/content/tracker/mpls-tp-openflow-protocol-extensions-for-sptn-becomes-a-formal-onf-standard-by-unanimous-approval-27467/">""MPLS-TP OpenFlow Protocol Extensions for SPTN" becomes a formal ONF standard by unanimous approval"</a>. June 27, 2017.</cite>

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> <cite id="CITEREFCamille_Campbell2014" class="citation web cs1">Camille Campbell (February 6, 2014). <a rel="nofollow" class="external text" href="https://www.avaya.com/blogs/archives/2014/02/avaya-debuts-networking-innovations-at-tech-field-day.html">"Avaya Debuts Networking Innovations at 'Tech Field Day'"</a>.</cite>

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> <cite id="CITEREFElizabeth_Miller_Coyne2016" class="citation news cs1">Elizabeth Miller Coyne (September 23, 2016). <a rel="nofollow" class="external text" href="http://www.lightreading.com/carrier-sdn/sdn-architectures/huawei-exec-sdns-become-a-completely-meaningless-term/d/d-id/726364">"Huawei Exec: SDN's Become a 'Completely Meaningless Term'"</a>. Light Reading.</cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.opennetworking.org/sdn-resources/sdn-definition">"Software-Defined Networking (SDN) Definition"</a>. Opennetworking.org. Retrieved 26 October 2014.</cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite id="CITEREFMontazerolghaemYaghmaeeLeon-Garcia2020" class="citation journal cs1">Montazerolghaem, Ahmadreza; Yaghmaee, Mohammad Hossein; Leon-Garcia, Alberto (September 2020). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/9044834">"Green Cloud Multimedia Networking: NFV/SDN Based Energy-Efficient Resource Allocation"</a>. IEEE Transactions on Green Communications and Networking. 4 (3): 873–889. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTGCN.2020.2982821">10.1109/TGCN.2020.2982821</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2473-2400">2473-2400</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:216188024">216188024</a>.</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.opennetworking.org/sdn-resources/sdn-library/whitepapers">"White Papers"</a>. Opennetworking.org. Retrieved 26 October 2014.</cite>

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite id="CITEREFMontazerolghaemYaghmaeeLeon-Garcia2017" class="citation journal cs1">Montazerolghaem, Ahmadreza.; Yaghmaee, M. H.; Leon-Garcia, A. (2017). "OpenSIP: Toward Software-Defined SIP Networking". IEEE Transactions on Network and Service Management. PP (99): 184–199. <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<a rel="nofollow" class="external text" href="https://arxiv.org/abs/1709.01320">1709.01320</a>. <a href="Bibcode_(identifier)" class="mw-redirect" title="Bibcode (identifier)">Bibcode</a>:<a rel="nofollow" class="external text" href="https://ui.adsabs.harvard.edu/abs/2017arXiv170901320M">2017arXiv170901320M</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2Ftnsm.2017.2741258">10.1109/tnsm.2017.2741258</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1932-4537">1932-4537</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:3873601">3873601</a>.</cite>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> <cite id="CITEREFVicentiniSantinViegasAbreu2019" class="citation journal cs1">Vicentini, Cleverton; Santin, Altair; Viegas, Eduardo; Abreu, Vilmar (January 2019). "SDN-based and multitenant-aware resource provisioning mechanism for cloud-based big data streaming". Journal of Network and Computer Applications. 126: 133–149. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.jnca.2018.11.005">10.1016/j.jnca.2018.11.005</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:57941895">57941895</a>.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite id="CITEREFAssefaÖzkasap2020" class="citation journal cs1">Assefa, Beakal Gizachew; Özkasap, Öznur (June 2020). <a rel="nofollow" class="external text" href="https://doi.org/10.1109/TNSM.2020.2973621">"RESDN: A Novel Metric and Method for Energy Efficient Routing in Software Defined Networks"</a>. IEEE Transactions on Network and Service Management. 17 (2): 736–749. <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<a rel="nofollow" class="external text" href="https://arxiv.org/abs/1905.12219">1905.12219</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTNSM.2020.2973621">10.1109/TNSM.2020.2973621</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:199442001">199442001</a>.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite id="CITEREFOliveiraXavier-de-SouzaSilveira2021" class="citation journal cs1">Oliveira, Tadeu F.; Xavier-de-Souza, Samuel; Silveira, Luiz F. (May 2021). <a rel="nofollow" class="external text" href="https://doi.org/10.3390%2Fen14113161">"Improving Energy Efficiency on SDN Control-Plane Using Multi-Core Controllers"</a>. Energies. 14 (11): 3161. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.3390%2Fen14113161">10.3390/en14113161</a>.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/SDN-architecture-overview-1.0.pdf">"SDN Architecture Overview"</a> (PDF). Opennetworking.org. Retrieved 22 November 2014.</cite>

</li>

<li id="cite_note-Yeganeh-33"><a href="#cite_ref-Yeganeh_33-0">^</a> <cite id="CITEREFYeganehGanjali" class="citation journal cs1">Yeganeh, S.H.; Ganjali, Y. <a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2342441.2342446">"Kandoo: A Framework for Efficient and Scalable Offloading of Control Applications"</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2342441.2342446">10.1145/2342441.2342446</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:193153">193153</a>.</cite> <code class="cs1-code">{{cite journal}}</code>: Cite journal requires <code class="cs1-code">|journal=</code> (help)

</li>

<li id="cite_note-Ahmed-34"><a href="#cite_ref-Ahmed_34-0">^</a> <cite id="CITEREFAhmedBoutaba2014" class="citation journal cs1">Ahmed, R.; Boutaba, R. (2014). "Design considerations for managing wide area software defined networks". IEEE Communications Magazine. 52 (7): 116–123. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMCOM.2014.6852092">10.1109/MCOM.2014.6852092</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:7912785">7912785</a>.</cite>

</li>

<li id="cite_note-Koponen-35"><a href="#cite_ref-Koponen_35-0">^</a> <cite id="CITEREFKoponen2010" class="citation journal cs1">Koponen, T. (2010). <a rel="nofollow" class="external text" href="https://www.usenix.org/legacy/events/osdi10/tech/full_papers/Koponen.pdf">"Onix: A Distributed Control Platform for Large scale Production Networks"</a> (PDF). Proceedings USENIX, Ser. OSDI'10. Vancouver, Canada.</cite>

</li>

<li id="cite_note-Tuncer1-36"><a href="#cite_ref-Tuncer1_36-0">^</a> <cite id="CITEREFTuncerCharalambidesClaymanPavlou2015" class="citation journal cs1">Tuncer, Daphne; Charalambides, Marinos; Clayman, Stuart; Pavlou, George (March 2015). <a rel="nofollow" class="external text" href="https://discovery.ucl.ac.uk/id/eprint/1478892/">"Adaptive Resource Management and Control in Software Defined Networks"</a>. IEEE Transactions on Network and Service Management. 12 (1): 18–33. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTNSM.2015.2402752">10.1109/TNSM.2015.2402752</a>. <a href="Hdl_(identifier)" class="mw-redirect" title="Hdl (identifier)">hdl</a>:<a rel="nofollow" class="external text" href="https://hdl.handle.net/10044%2F1%2F63600">10044/1/63600</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:9215618">9215618</a>.</cite>

</li>

<li id="cite_note-Heller-37"><a href="#cite_ref-Heller_37-0">^</a> <cite id="CITEREFHellerSherwoodMcKeown2012" class="citation book cs1">Heller, B.; Sherwood, R.; McKeown, N. (2012). "The Controller Placement Problem". Proceedings of the first workshop on Hot topics in software defined networks - HotSDN '12. p. 7. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2342441.2342444">10.1145/2342441.2342444</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781450314770</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:1770114">1770114</a>.</cite>

</li>

<li id="cite_note-Hu-38"><a href="#cite_ref-Hu_38-0">^</a> <cite id="CITEREFHuWangGongQue2012" class="citation journal cs1">Hu, Yan-nan; Wang, Wen-Dong; Gong, Xiang-Yang; Que, Xi-Rong; Cheng, Shi-Duan (2012). "On the placement of controllers in software-defined networks". The Journal of China Universities of Posts and Telecommunications. 19: 92–171. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2FS1005-8885%2811%2960438-X">10.1016/S1005-8885(11)60438-X</a>.</cite>

</li>

<li id="cite_note-Ros-39"><a href="#cite_ref-Ros_39-0">^</a> <cite id="CITEREFRosRuiz2014" class="citation book cs1">Ros, Francisco Javier; Ruiz, Pedro Miguel (2014). "Five nines of southbound reliability in software-defined networks". Proceedings of the third workshop on Hot topics in software defined networking. pp. 31–36. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2620728.2620752">10.1145/2620728.2620752</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781450329897</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17088018">17088018</a>.</cite>

</li>

<li id="cite_note-Tuncer2-40"><a href="#cite_ref-Tuncer2_40-0">^</a> <cite id="CITEREFTuncerCharalambidesClaymanPavlou2015" class="citation book cs1">Tuncer, Daphne; Charalambides, Marinos; Clayman, Stuart; Pavlou, George (2015). "On the Placement of Management and Control Functionality in Software Defined Networks". <a rel="nofollow" class="external text" href="https://discovery.ucl.ac.uk/id/eprint/1502968/">2015 11th International Conference on Network and Service Management (CNSM)</a>. pp. 360–365. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FCNSM.2015.7367383">10.1109/CNSM.2015.7367383</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-3-9018-8277-7</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:6977724">6977724</a>.</cite>

</li>

<li id="cite_note-wang.2014.scotch-41"><a href="#cite_ref-wang.2014.scotch_41-0">^</a> <cite id="CITEREFWangGuoHaoLakshman2014" class="citation journal cs1">Wang, An; Guo, Yang; Hao, Fang; Lakshman, T.; Chen, Songqing (2 December 2014). <a rel="nofollow" class="external text" href="http://conferences2.sigcomm.org/co-next/2014/CoNEXT_papers/p403.pdf">"Scotch: Elastically Scaling up SDN Control-Plane using vSwitch based Overlay"</a> (PDF). ACM CoNEXT.</cite>

</li>

<li id="cite_note-42"><a href="#cite_ref-42">^</a> <cite id="CITEREFTaylorMacFarlandSmestadShue2014" class="citation book cs1">Taylor, Curtis; MacFarland, Douglas; Smestad, Doran; Shue, Craig (10 April 2014). <a rel="nofollow" class="external text" href="https://par.nsf.gov/servlets/purl/10055769">"Contextual, flow-based access control with scalable host-based SDN techniques"</a>. IEEE INFOCOM 2016 - the 35th Annual IEEE International Conference on Computer Communications. pp. 1–9. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FINFOCOM.2016.7524498">10.1109/INFOCOM.2016.7524498</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-9953-1</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17491115">17491115</a>.</cite>

</li>

<li id="cite_note-43"><a href="#cite_ref-43">^</a> <cite id="CITEREFChuluundorjTaylorWallsShue2021" class="citation book cs1">Chuluundorj, Zorigtbaatar; Taylor, Curtis; Walls, Robert; Shue, Craig (6 December 2021). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/9732164">"Can the User Help? Leveraging User Actions for Network Profiling"</a>. 2021 Eighth International Conference on Software Defined Systems (SDS). pp. 1–8. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSDS54264.2021.9732164">10.1109/SDS54264.2021.9732164</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-6654-5820-7</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:244036711">244036711</a>.</cite>

</li>

<li id="cite_note-44"><a href="#cite_ref-44">^</a> <cite id="CITEREFLeiLansonKaldawyEstrada2020" class="citation book cs1">Lei, Yunsen; Lanson, Julian; Kaldawy, Remy; Estrada, Jeffrey; Shue, Craig (11 November 2020). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/9249110">"Can Host-Based SDNS Rival the Traffic Engineering Abilities of Switch-Based SDNS?"</a>. 2020 11th International Conference on Network of the Future (NoF). pp. 91–99. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FNoF50125.2020.9249110">10.1109/NoF50125.2020.9249110</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-7281-8055-7</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:221505891">221505891</a>.</cite>

</li>

<li id="cite_note-45"><a href="#cite_ref-45">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://networkstatic.net/openflow-proactive-vs-reactive-flows/">"OpenFlow: Proactive vs Reactive"</a>. NetworkStatic.net. 2013-01-15. Retrieved 2014-07-01.</cite>

</li>

<li id="cite_note-46"><a href="#cite_ref-46">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://devcentral.f5.com/articles/reactive-proactive-predictive-sdn-models">"Reactive, Proactive, Predictive: SDN Models | F5 DevCentral"</a>. Devcentral.f5.com. 2012-10-11. Retrieved 2016-06-30.</cite>

</li>

<li id="cite_note-MobileFlow-47"><a href="#cite_ref-MobileFlow_47-0">^</a> <cite id="CITEREFPentikousisWangHu2013" class="citation journal cs1">Pentikousis, Kostas; Wang, Yan; Hu, Weihua (2013). "Mobileflow: Toward software-defined mobile networks". IEEE Communications Magazine. 51 (7): 44–53. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMCOM.2013.6553677">10.1109/MCOM.2013.6553677</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:10655582">10655582</a>.</cite>

</li>

<li id="cite_note-48"><a href="#cite_ref-48">^</a> <cite id="CITEREFLiyanage2015" class="citation book cs1">Liyanage, Madhusanka (2015). <a rel="nofollow" class="external text" href="http://eu.wiley.com/WileyCDA/WileyTitle/productCd-1118900286.html">Software Defined Mobile Networks (SDMN): Beyond LTE Network Architecture</a>. UK: John Wiley. pp. 1–438. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-118-90028-4</bdi>.</cite>

</li>

<li id="cite_note-49"><a href="#cite_ref-49">^</a> <cite id="CITEREFCosta-RequenaLiyanageYlianttilaDe_Oca2015" class="citation book cs1">Costa-Requena, Jose; Liyanage, Madhusanka; Ylianttila, Mika; De Oca, Edgardo Montes; Santos, Jesus Llorente; Guasch, Vicent Ferrer; Ahokas, Kimmo; Premsankar, Gopika; Luukkainen, Sakari; Perez, Oscar Lopez; Itzazelaia, Mikel Uriarte; Ahmad, Ijaz (2015). "SDN and NFV Integration in Generalized Mobile Network Architecture". 2015 European Conference on Networks and Communications (EuCNC). pp. 154–158. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FEuCNC.2015.7194059">10.1109/EuCNC.2015.7194059</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-7359-3</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:2453962">2453962</a>.</cite>

</li>

<li id="cite_note-50"><a href="#cite_ref-50">^</a> <cite id="CITEREFLiyanageYlianttilaGurtov2014" class="citation book cs1">Liyanage, Madhusanka; Ylianttila, Mika; Gurtov, Andrei (2014). "Securing the Control Channel of Software-Defined Mobile Networks". Proceeding of IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks 2014. pp. 1–6. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FWoWMoM.2014.6918981">10.1109/WoWMoM.2014.6918981</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4799-4786-7</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:1378181">1378181</a>.</cite>

</li>

<li id="cite_note-51"><a href="#cite_ref-51">^</a> <cite id="CITEREFHaranas2016" class="citation web cs1">Haranas, Mark (8 October 2016). <a rel="nofollow" class="external text" href="http://www.crn.com/slide-shows/networking/300082325/16-hot-networking-products-putting-the-sizzle-in-sd-wan.htm?itc=hp_slideshow">"16 Hot Networking Products Putting The Sizzle In SD-WAN"</a>. CRN. Retrieved 1 November 2016.</cite>

</li>

<li id="cite_note-networkworld1-52"><a href="#cite_ref-networkworld1_52-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.networkworld.com/article/947944/sd-wan-what-it-is-and-why-you-ll-use-it-one-day.html">"SD-WAN: What it is and why you'll use it one day"</a>. <a href="Network_World" class="mw-redirect" title="Network World">Network World</a>. 2016-02-10. Retrieved 2016-06-27.</cite>

</li>

<li id="cite_note-53"><a href="#cite_ref-53">^</a> <cite id="CITEREFSerries2016" class="citation web cs1">Serries, William (12 September 2016). <a rel="nofollow" class="external text" href="http://www.zdnet.fr/actualites/sd-lan-et-sd-wan-deux-approches-differentes-pour-le-software-defined-networking-39841794.htm">"SD-LAN et SD-WAN : Deux Approches Différentes pour le Software Defined Networking"</a>. ZDNet. Retrieved 1 November 2016.</cite>

</li>

<li id="cite_note-54"><a href="#cite_ref-54">^</a> <cite id="CITEREFKerravala2016" class="citation web cs1">Kerravala, Zeus (13 September 2016). <a rel="nofollow" class="external text" href="https://www.networkworld.com/article/955256/aerohive-introduces-the-software-defined-lan.html">"Aerohive Introduces the Software-defined LAN"</a>. Network World. Retrieved 1 November 2016.</cite>

</li>

<li id="cite_note-kreutz2013towards-55"><a href="#cite_ref-kreutz2013towards_55-0">^</a> <cite id="CITEREFKreutz,_DiegoRamos,_FernandoVerissimo,_Paulo2013" class="citation conference cs1">Kreutz, Diego; Ramos, Fernando; Verissimo, Paulo (2013). "Towards secure and dependable software-defined networks". Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking. pp. 50–60.</cite>

</li>

<li id="cite_note-scott2013sdn-56"><a href="#cite_ref-scott2013sdn_56-0">^</a> <cite id="CITEREFScott-Hayward,_SandraO'Callaghan,_GemmaSezer,_Sakir2013" class="citation conference cs1">Scott-Hayward, Sandra; O'Callaghan, Gemma; Sezer, Sakir (2013). "SDN security: A survey". Future Networks and Services (SDN4FNS), 2013 IEEE SDN for. pp. 1–7.</cite>

</li>

<li id="cite_note-benton2013openflow-57"><a href="#cite_ref-benton2013openflow_57-0">^</a> <cite id="CITEREFBenton,_KevinCamp,_L_JeanSmall,_Chris2013" class="citation conference cs1">Benton, Kevin; Camp, L Jean; Small, Chris (2013). "Openflow vulnerability assessment". Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking. pp. 151–152.</cite>

</li>

<li id="cite_note-58"><a href="#cite_ref-58">^</a> <cite id="CITEREFAbdouvan_OorschotWan2018" class="citation journal cs1 cs1-prop-long-vol">Abdou, AbdelRahman; van Oorschot, Paul; Wan, Tao (May 2018). "A Framework and Comparative Analysis of Control Plane Security of SDN and Conventional Networks". IEEE Communications Surveys and Tutorials. to appear. <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<a rel="nofollow" class="external text" href="https://arxiv.org/abs/1703.06992">1703.06992</a>. <a href="Bibcode_(identifier)" class="mw-redirect" title="Bibcode (identifier)">Bibcode</a>:<a rel="nofollow" class="external text" href="https://ui.adsabs.harvard.edu/abs/2017arXiv170306992A">2017arXiv170306992A</a>.</cite>

</li>

<li id="cite_note-giotis2014combining-59"><a href="#cite_ref-giotis2014combining_59-0">^</a> <cite id="CITEREFGiotis,_KArgyropoulos,_ChristosAndroulidakis,_GeorgiosKalogeras,_Dimitrios2014" class="citation journal cs1">Giotis, K; Argyropoulos, Christos; Androulidakis, Georgios; Kalogeras, Dimitrios; Maglaris, Vasilis (2014). <a rel="nofollow" class="external text" href="https://zenodo.org/record/3415467">"Combining OpenFlow and sFlow for an effective and scalable anomaly detection and mitigation mechanism on SDN environments"</a>. Computer Networks. 62: 122–136. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.bjp.2013.10.014">10.1016/j.bjp.2013.10.014</a>.</cite>

</li>

<li id="cite_note-braga2010lightweight-60"><a href="#cite_ref-braga2010lightweight_60-0">^</a> <cite id="CITEREFBraga,_RodrigoMota,_EdjardPassito,_Alexandre2010" class="citation conference cs1">Braga, Rodrigo; Mota, Edjard; Passito, Alexandre (2010). "Lightweight DDoS flooding attack detection using NOX/OpenFlow". Local Computer Networks (LCN), 2010 IEEE 35th Conference on. pp. 408–415.</cite>

</li>

<li id="cite_note-feamster2010outsourcing-61"><a href="#cite_ref-feamster2010outsourcing_61-0">^</a> <cite id="CITEREFFeamster,_Nick2010" class="citation conference cs1">Feamster, Nick (2010). "Outsourcing home network security". Proceedings of the 2010 ACM SIGCOMM workshop on Home networks. pp. 37–42.</cite>

</li>

<li id="cite_note-jin2013malware-62"><a href="#cite_ref-jin2013malware_62-0">^</a> <cite id="CITEREFJin,_RuofanWang,_Bing2013" class="citation conference cs1">Jin, Ruofan & Wang, Bing (2013). "Malware detection for mobile devices using software-defined networking". Research and Educational Experiment Workshop (GREE), 2013 Second GENI. 81-88.</cite><code class="cs1-code">{{cite conference}}</code>: CS1 maint: location (link)

</li>

<li id="cite_note-jafarian2012openflow-63"><a href="#cite_ref-jafarian2012openflow_63-0">^</a> <cite id="CITEREFJafarian,_Jafar_HaadiAl-Shaer,_EhabDuan,_Qi2012" class="citation conference cs1">Jafarian, Jafar Haadi; Al-Shaer, Ehab; Duan, Qi (2012). "Openflow random host mutation: transparent moving target defense using software defined networking". Proceedings of the first workshop on Hot topics in software defined networks. pp. 127–132.</cite>

</li>

<li id="cite_note-kampanakissdn-64"><a href="#cite_ref-kampanakissdn_64-0">^</a> <cite id="CITEREFKampanakis,_PanosPerros,_HarryBeyene,_Tsegereda" class="citation conference cs1">Kampanakis, Panos; Perros, Harry; Beyene, Tsegereda. <a rel="nofollow" class="external text" href="https://people.engr.ncsu.edu/hp/papers/Panos.pdf">SDN-based solutions for Moving Target Defense network protection</a> (PDF). Retrieved 16 February 2022.</cite>

</li>

<li id="cite_note-sherwood2009flowvisor-65">^ <a href="#cite_ref-sherwood2009flowvisor_65-0">a</a> <a href="#cite_ref-sherwood2009flowvisor_65-1">b</a> <cite id="CITEREFSherwood,_RobGibb,_GlenYap,_Kok-KiongAppenzeller,_Guido2009" class="citation journal cs1">Sherwood, Rob; Gibb, Glen; Yap, Kok-Kiong; Appenzeller, Guido; Casado, Martin; McKeown, Nick; Parulkar, Guru (2009). "Flowvisor: A network virtualization layer". OpenFlow Switch Consortium, Tech. Rep.</cite>

</li>

<li id="cite_note-al2010flowchecker-66"><a href="#cite_ref-al2010flowchecker_66-0">^</a> <cite id="CITEREFAl-Shaer,_EhabAl-Haj,_Saeed2010" class="citation conference cs1">Al-Shaer, Ehab & Al-Haj, Saeed (2010). "FlowChecker: Configuration analysis and verification of federated OpenFlow infrastructures". Proceedings of the 3rd ACM workshop on Assurable and usable security configuration. pp. 37–44.</cite>

</li>

<li id="cite_note-canini2012nice-67"><a href="#cite_ref-canini2012nice_67-0">^</a> <cite id="CITEREFCanini,_MarcoVenzano,_DanielePeresini,_PeterKostic,_Dejan2012" class="citation conference cs1">Canini, Marco; Venzano, Daniele; Peresini, Peter; Kostic, Dejan; Rexford, Jennifer; et al. (2012). A NICE Way to Test OpenFlow Applications. NSDI. pp. 127–140.</cite>

</li>

<li id="cite_note-bernardo2015sn-seca-68"><a href="#cite_ref-bernardo2015sn-seca_68-0">^</a> <cite id="CITEREFBernardo_and_Chua2015" class="citation conference cs1">Bernardo and Chua (2015). Introduction and Analysis of SDN and NFV Security Architecture (SA-SECA). 29th IEEE AINA 2015. pp. 796–801.</cite>

</li>

<li id="cite_note-69"><a href="#cite_ref-69">^</a> <cite id="CITEREFB._Pfaf2011" class="citation web cs1">B. Pfaf; et al. (February 28, 2011). <a rel="nofollow" class="external text" href="http://archive.openflow.org/documents/openflow-spec-v1.1.0.pdf">"OpenFlow Switch Specification"</a> (PDF). Retrieved July 8, 2017.</cite>

</li>

<li id="cite_note-70"><a href="#cite_ref-70">^</a> <cite id="CITEREFT._Zhu2016" class="citation book cs1">T. Zhu; et al. (October 18, 2016). "MCTCP: Congestion-aware and robust multicast TCP in Software-Defined networks". 2016 IEEE/ACM 24th International Symposium on Quality of Service (IWQoS). IEEE. pp. 1–10. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FIWQoS.2016.7590433">10.1109/IWQoS.2016.7590433</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-5090-2634-0</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:28159768">28159768</a>.</cite>

</li>

<li id="cite_note-71"><a href="#cite_ref-71">^</a> <cite id="CITEREFM._Noormohammadpour2017" class="citation web cs1">M. Noormohammadpour; et al. (July 10, 2017). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/316921061">"DCCast: Efficient Point to Multipoint Transfers Across Datacenters"</a>. USENIX. Retrieved July 3, 2017.</cite>

</li>

<li id="cite_note-72"><a href="#cite_ref-72">^</a> <cite id="CITEREFM._Noormohammadpour2018" class="citation book cs1">M. Noormohammadpour; et al. (2018). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/322243498">QuickCast: Fast and Efficient Inter-Datacenter Transfers using Forwarding Tree Cohorts</a>. <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<a rel="nofollow" class="external text" href="https://arxiv.org/abs/1801.00837">1801.00837</a>. <a href="Bibcode_(identifier)" class="mw-redirect" title="Bibcode (identifier)">Bibcode</a>:<a rel="nofollow" class="external text" href="https://ui.adsabs.harvard.edu/abs/2018arXiv180100837N">2018arXiv180100837N</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.31219%2Fosf.io%2Fuzr24">10.31219/osf.io/uzr24</a>. Retrieved January 23, 2018.</cite>

</li>

<li id="cite_note-Stalling2016-73">^ <a href="#cite_ref-Stalling2016_73-0">a</a> <a href="#cite_ref-Stalling2016_73-1">b</a> <cite id="CITEREFWilliam2016" class="citation journal cs1">William, Stalling (2016). "Foundations of Modern Networking: SDN, NFV, QoE, IoT, and Cloud". Pearson Education.</cite>

</li>

<li id="cite_note-Rowayda2018-74"><a href="#cite_ref-Rowayda2018_74-0">^</a> <cite id="CITEREFRowayda2018" class="citation journal cs1">Rowayda, A. Sadek (May 2018). "An Agile Internet of Things (IoT) based Software Defined Network (SDN) Architecture". Egyptian Computer Science Journal. 42 (2): 13–29.</cite>

</li>

<li id="cite_note-75"><a href="#cite_ref-75">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.cisco.com/go/esp">"Platform to Multivendor Virtual and Physical Infrastructure"</a>.</cite>

</li>

<li id="cite_note-76"><a href="#cite_ref-76">^</a> <cite id="CITEREFGraham2012" class="citation journal cs1">Graham, Finnie (December 2012). "The Role Of DPI In An SDN World". White Paper.</cite>

</li>

<li id="cite_note-ITUDPI-77"><a href="#cite_ref-ITUDPI_77-0">^</a> <cite id="CITEREFSeries2015" class="citation journal cs1">Series, Y. (May 2015). "Global Information Infrastructure, Internet Protocol Aspects And Next Generation Networks". ITU-T Y.2770 Series, Supplement on DPI Use Cases and Application Scenarios.</cite>

</li>

<li id="cite_note-78"><a href="#cite_ref-78">^</a> <cite id="CITEREFCanovas2020" class="citation journal cs1">Canovas, Alejandro (2020). <a rel="nofollow" class="external text" href="https://www.sciencedirect.com/science/article/pii/S1084804519303583">"A robust multimedia traffic SDN-Based management system using patterns and models of QoE estimation with BRNN"</a>. Journal of Network and Computer Applications. 150: 102498. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.jnca.2019.102498">10.1016/j.jnca.2019.102498</a>. <a href="Hdl_(identifier)" class="mw-redirect" title="Hdl (identifier)">hdl</a>:<a rel="nofollow" class="external text" href="https://hdl.handle.net/10251%2F163292">10251/163292</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:210925444">210925444</a>.</cite>

</li>

<li id="cite_note-79"><a href="#cite_ref-79">^</a> <cite id="CITEREFRego2019" class="citation journal cs1">Rego, Albert (2019). <a rel="nofollow" class="external text" href="https://onlinelibrary.wiley.com/doi/abs/10.1002/ett.3643">"Adapting reinforcement learning for multimedia transmission on SDN"</a>. Transactions on Emerging Telecommunications Technologies. 30 (9). <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1002%2Fett.3643">10.1002/ett.3643</a>. <a href="Hdl_(identifier)" class="mw-redirect" title="Hdl (identifier)">hdl</a>:<a rel="nofollow" class="external text" href="https://hdl.handle.net/10251%2F186852">10251/186852</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:182028234">182028234</a>.</cite>

</li>

</ol></div></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q1655198#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata647" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q1655198#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata647" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh2014000092">United States</a></li><li><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007579386805171">Israel</a></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/f84769d7-ae09-49b2-a1f5-31b16c990317">Yale LUX</a></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-24" href="https://en.wikipedia.org/wiki/?title=Software-defined_networking&oldid=1302225797">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>